ci(release): adopt verified release PR pipeline#255
Conversation
Deploying podnotes with
|
| Latest commit: |
0afd870
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f18dc747.podnotes.pages.dev |
| Branch Preview URL: | https://ci-release-pr-pipeline.podnotes.pages.dev |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0afd8709bc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const openPulls = await github.paginate(github.rest.pulls.list, { | ||
| owner, | ||
| repo, | ||
| state: 'open', | ||
| head: `${owner}:${branch}`, | ||
| per_page: 100, |
There was a problem hiding this comment.
Close superseded release PRs before opening a new one
When a release PR is already open and a later master commit changes the planned bump (for example, patch to minor), this only searches for the new release/${version} branch, leaving the older bot-generated release/* PR open with its previously dispatched Test check. If that stale PR is merged, release-trigger.yml rejects it because the squash parent no longer matches the recorded base, but the stale version bump has already landed on master; close or invalidate other generated release PRs when a new plan supersedes them.
Useful? React with 👍 / 👎.
Summary
main.jsandmanifest.json, re-download and hash the uploaded assets, and publish the draft release only after verificationnpm versionpath and@semantic-release/gitSecurity model
Validation
npm cinpm run lintnpm run format:checknpm run typechecknpm run buildnpm run test- 71 files, 909 testsuv run --with-requirements docs/requirements.txt mkdocs build -f docs/mkdocs.yml -d sitenpm audit --audit-level=high- 0 vulnerabilities2.17.46f593e89c049bc84a8a9b3da90a5f002ccc5b8e1066ae05aef671dbc12cd5ebcCanary prerequisite
Keep this PR draft until release-PR authentication is selected. The repository currently blocks
GITHUB_TOKENfrom creating or approving PRs. Before merge, either enable that repository switch, provide a narrowly scoped GitHub App token, or change release PR opening to a manual maintainer step.